Progress Tracking
- Explain the purpose of a 121
- Prepare effectively for a 121
- Describe what is a good or bad 121 topic
Pre-work
No pre-work is required for this workshop.
Workshop
Draw on the board the three pillars of technical progress tracking:
- Mastery Quiz
- Technical Assessment
- Coach Assessment
Discuss positives and limitations of each, then ask trainees to give an example scenario for when each would highlight a gap.
Explain that we track behaviours via:
- Observations by coaches
- Automated data (attendance, punctuality, commit history)
- Peer feedback (MVP nominations, actionable comments)
Weekly Tracking
Outline the flow:
- Inputs: All of the above
- Outputs: A dashboard summarising competency progress, qualitative feedback, next-week objectives
- Meetings: weekly 121 in weeks 1-3; fortnightly thereafter (or more often if needed)
Discuss how this cycle supports continuous improvement.
What is a 121?
Explain that a 121 is:
- A 15-20 minute planned meeting led by the trainee
- A forum to share successes, struggles, future objectives, and mutual feedback
- Not for deep technical debugging or retrospective complaints
Review the standard agenda:
- Your planned talking points
- Talk through any feedback you’ve received
- Agreed objectives for next week
Clarify cadence:
- Weekly in the first three weeks
- Fortnightly thereafter (unless more frequent check-ins are requested)
Emphasise trainee responsibility:
- Prepare talking points beforehand
- Take and share notes after each meeting
121 Task
Provide the trainees with a list of sample agenda items:
A) “I’m struggling with understanding async programming concepts in JavaScript. Can we go through it?”
B) “I’m finding it hard to keep up the content. Have you got any advice?”
C) “I’m binge-watching the latest Netflix series and stayed up all night, so I might not be very productive today.”
D) “I’ve come across a subscription to a coding platform that offers hands-on projects. Can I get access to it?”
E) “What else could I be doing to increase my Proactivity score?”
F) “The coding tools we use are terrible.”
G) “I’ve noticed Gary (another trainee) has been a bit down this week.”
H) “Here are my goals for the next week - what do you think?”
I) “My dog is really sick, and I’m worried it’s going to affect my work.”
J) “I didn’t finish the coursework.”
K) “I think you could improve the course by making [this] change.”
L) “Here’s a list of things I’ve done that I’m proud of this week.”
M) “My code doesn’t work, can you help?”
N) “Could I get more information about why my Content Mastery score is low?”
O) “There’s been construction work in my house, which is why I didn’t finish the coursework.”
P) “I’ve noticed Gary (another trainee) is struggling with problem solving.”
Q) “I haven’t finished the coursework, but here is what I’m going to change to ensure it doesn’t happen again.”
Tell the trainees, in small groups, sort each item into “Good 121 topic” or “Bad 121 topic.”
Debrief: Discuss why certain items are effective and others are not.